The PDMx Project Repository Manager is used to manage projects. The projects consist of the PDMx xml files as well as the configuration settings. The Repository Manager allows users to create New projects, Clone existing projects, Rename, Edit, Delete and explore the Project Folder.

In the following example there are two projects in the Project Repository Manager:

The Project Repository has the following folder structure with two sample projects:

The Project folder structure is shown below. Each project contains a configuration file - Project.xml file the contains the settings along with the ExportFiles folder that contains the pdmx.xml files exported from AVEVA PDMS or E3D. Additional schema files, session folders and logs can be generated in the project folder during conversion.

The picture below shows the creation of a new project with the with default project settings. In this case the PDMx xml files will come from the ExportFiles folder. The list of files from this folder will be used as filters by the Plant Exporter or Open 3D Model Bridge.

You can use custom scripts to get filters directly from AVEVA PDMS or E3D. To use this option, click on Connect to PDMS and then select the Start script, PDMS path to batch file used to start PDMS, the Project name, the MDB name, as well as User name and Password. In this case PDMx xml files from ExportFiles folder will be ignored.

Check Generate STEP export for GENPRI/GENCUR elements if you want these exports to be part of your conversions from E3D or PDMS. Checking this box results in a folder created at the same level as the pdmx.xml file and the STEP exports will be contained in this folder.

After export, you can embed the STEP file contents into the pdmx.xml file by selecting a project and clicking the Embed STEP files button.

Advanced

In the Advanced dialog on the Representation tab, the levels for different categories of components can be set as well as options to include insulation, obstructions and cableway volumes.

The GEO Location tab allows you to set the geo location of a model in the iModel when enabled. If an iModel does not have any geo location data set when the iModel Bridge converts data and you have set geo location data, the geo location data set in this interface is be set for the entire iModel. If geo location data is already set, the data from this model will use the data provided and set the model to the provided geo location.